docs(feature-guide) Impact Analysis #5765
Conversation
|
|
||
| ### Feature Guide | ||
|
|
||
| A Feature Guide should follow the [Feature Guide Template](/_feature-guide-template.md), and should provide the following value: |
There was a problem hiding this comment.
@jjoyce0510 looking for your input here
maggiehays
added
docs
|
|
||
| <FeatureAvailability/> | ||
|
|
||
| Impact Analysis is a powerful workflow for understanding the full set of upstream and downstream dependencies of a Dataset, Dashboard, Chart, and many other DataHub Entites. |
There was a problem hiding this comment.
It's a bit confusing -- is Impact Analysis a specific concept ? Or a feature?
To me we should just call this "Lineage" to avoid confusion. People will click "Lineage" to use the feature! Specific workflows can be a subset
There was a problem hiding this comment.
@jjoyce0510 hmmm.. great question. We have a separate Lineage section under "Enrich Metadata", focused on the various ways you can ingest Lineage (Vineetha is on point to build out a better guide, basically building a guide off of our DataHub 101: Lineage video).
This one falls under the "Act on Metadata" section, so I think it still makes sense to call it Impact Analysis. I know we took that terminology out of the UI, but we continue to refer to it as the main lineage-related workflow. My preference would be to keep it as-is for now.
What do you think?
There was a problem hiding this comment.
@jjoyce0510 just saw @hsheth2's note about high search volume for the term Lineage. How about we meet in the middle & I rephrase it as Lineage Impact Analysis?
Co-authored-by: Harshal Sheth <[email protected]>
This PR includes:
Checklist